<!DOCTYPE doctype PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN">

<HTML>
  <HEAD>
    <META name="generator" content=
    "HTML Tidy for Java (vers. 2009-12-01), see jtidy.sourceforge.net">

    <TITLE>Debugger: Targets</TITLE>
    <META http-equiv="Content-Type" content="text/html; charset=windows-1252">
    <LINK rel="stylesheet" type="text/css" href="help/shared/DefaultStyle.css">
  </HEAD>

  <BODY lang="EN-US">
    <H1><A name="plugin"></A>Debugger: Targets</H1>

    <DIV class="image">
      <IMG alt="" src="images/DebuggerTargetsPlugin.png">
    </DIV>

    <P><IMG alt="" src="help/shared/note.png">This window only supports the older "Recorder-based"
    targets. For newer "TraceRmi-based" targets, see the Connection Manager window.</P>

    <P>The targets window manages connections to live debuggers. In most cases, each item is a
    GADP/TCP connection to a local "agent" process which manages a native debugger, communicating
    information about its targets. It is possible, however, to create a connection without starting
    an agent, e.g., to re-connect to an existing agent, or a remote agent. Additionally, different
    connectors may implement alternative protocols, or use a debugging API directly. This window
    allows the user to establish and terminate connections.</P>

    <H2>Actions</H2>

    <P>This window provides the following actions for managing connections.</P>

    <H3><A name="connect"></A><IMG alt="" src="icon.debugger.connect"> Connect</H3>

    <P>Prompts the user to select a connector and configure its parameters.</P>

    <DIV class="image">
      <IMG alt="" src="images/DebuggerConnectDialog.png">
    </DIV>

    <P>The top drop-down displays a list of pluggable connectors. A description and the options for
    the currently-selected connector are displayed below. Some will start a new session, while
    others may simply connect to an existing session. Each connector defines its own options, but
    common ones include port numbers, host names, the system paths of debugging components, etc.
    Each connector should provide help in the form of tool tips, accessed by hovering over an
    option's name. Clicking "Connect" will start the connector and dismiss the dialog.</P>

    <H3><A name="disconnect"></A><IMG alt="" src="icon.debugger.disconnect"> Disconnect</H3>

    <P>This action is available when a connection is selected. It closes the connection. Note,
    depending on the robustness of the connector's termination logic, this may not clean up all
    processes created by the connector.</P>

    <H3><A name="disconnect_all"></A> Disconnect All</H3>

    <P>This action is always available. It closes all debugger connections, no matter what tool
    created them. This is a sort of panic and reset action. As with Disconnect, clean-up depends on
    each connector's implementation.</P>

    <H3><A name="flush_caches"></A>Flush Caches</H3>

    <P>This maintenance command instructs the selected connector to flush its local caches. It
    should rarely, if ever, be needed by the user. It may be useful if, e.g., stale memory is not
    getting updated.</P>
  </BODY>
</HTML>
